System and method for assigning a network address

ABSTRACT

A method relates to a network identification that uniquely identifies a communication device. The method includes determining a network address corresponding to the network identification. Another step is determining which device manager, of multiple device managers, is assigned the network address. Information and the network address is transmitted to the assigned device manager. The assigned device manager determines, from the network address, a device identification that identifies the wireless device within a communication device network. Using the device identification, the assigned device manager transmits the information to the device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.11/510,376, filed on Aug. 25, 2006 now U.S. Pat. No. 7,251,486, which isa continuation of U.S. patent application Ser. No. 10/831,263, filedApr. 23, 2004 (now U.S. Pat. No. 7,120,438), which are herebyincorporated herein by reference.

FIELD

This technology relates generally to wireless communications andassigning network addresses.

BACKGROUND

Systems for transmitting data to and from a wireless device are known inthis field. The technology described in this patent application,however, overcomes many of the deficiencies of these known systems byproviding unique network identifications for multiple wireless deviceswithin the system that enable data to be transmitted through a computernetwork to a wireless device using a network address, such as aninternet protocol (IP) address.

SUMMARY

A method relates to a network identification that uniquely identifies acommunication device. The method includes determining a network addresscorresponding to the network identification. Another step is determiningwhich device manager, of multiple device managers, is assigned thenetwork address. Information and the network address is transmitted tothe assigned device manager. The assigned device manager determines,from the network address, a device identification that identifies thewireless device within a communication device network. Using the deviceidentification, the assigned device manager transmits the information tothe device.

Preferably, the communication device is a wireless communication device,and the device network is a wireless network. Before the determiningsteps, the information and the network identification are received froma computer network server. The network identification includes a domainname and a host name.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example system for pushing data from aninformation source to a wireless device using a network identificationassociated with the wireless device;

FIG. 2 is a diagram illustrating one example implementation of thesystem of FIG. 1;

FIG. 3 is a diagram showing one example of how data may be pushed froman information source to a wireless device using the system of FIG. 2;

FIG. 4 is a diagram of an example system for transmitting data from afirst wireless device through a computer network to a second wirelessdevice using a network identification associated with the secondwireless device;

FIG. 5 is a diagram illustrating one example implementation of thesystem of FIG. 4 in which the first and second wireless devices areassociated with the same computer network;

FIG. 6 is a diagram showing one example of how data may be transmittedfrom a first wireless device to a second wireless device using thesystem of FIG. 5; and

FIGS. 7 and 8 are diagrams illustrating example implementations of thesystem of FIG. 4 in which the first and second wireless devices areassociated with different computer networks.

DETAILED DESCRIPTION

Referring now to the drawing figures, FIG. 1 is a diagram of an examplesystem 10 for pushing data 11 from an information source 12 to awireless device 14 using a network identification 16 associated with thewireless device 14. In addition to the information source 12 andwireless device 14, the system 10 includes a network server 18, avirtual device manager 20, and an address resolution (AR) module 22.

The information source 12 may, for example, be an Internet or webserver, a software application executing on a processor coupled to acomputer network, or some other type of information source capable ofcommunicating with a computer network. The data 11 and networkidentification 16 may be stored in a memory device accessible by theinformation source 12, may be input to the information source 12 througha user interface or from another device or system, or may be acquired bythe information source 12 using some other known method. The networkidentification 16 may, for example, identify both a host name for thewireless device 14 and a domain name for the network server 18, butcould also be some other type of suitable network identification.

The network server 18 may, for example, be a domain name server (DNS)operating in a computer network. The network server 18 is operable toreceive a network identification 16, such as a domain name and hostname, and identify a network address 24 associated with the networkidentification 16. For example, in the case of a domain name serveroperating on a TCP/IP network, the network server 18 may receive adomain name identification and a host name identification, and resolvethe domain and host names into an internet protocol (IP) address thatidentifies a device on the TCP/IP network that is associated with thehost name.

The virtual device manager 20 may, for example, be a processing deviceoperating in a computer network. The virtual device manager 20 may beaccessed on the computer network using any of a plurality of networkaddresses, with each of the network addresses corresponding to adifferent wireless device. That is, the network address 24 correspondingto the wireless device 14 is assigned, either statically or dynamically,to the virtual device manager 20. In addition, network addressescorresponding to other wireless devices are also assigned to the virtualdevice manager 20, such that the virtual device manager 20 may service agroup of wireless devices.

The address resolution (AR) module 22 may, for example, be a softwaremodule executing on a processing device operating in a computer network.In one embodiment, for example, the AR module 22 may be executed by thevirtual device manager 20, or by another processor coupled through thecomputer network to the virtual device manager 20. The AR module 22 isoperable to receive a network address 24, such as an IP address, andidentify a wireless identification 26 for the wireless device 14corresponding to the network address 24. For example, the AR module 22may access a lookup table to match the network address 24 received bythe virtual device manager 20 with a Mobile Access Number (MAN), orother type of wireless identification 26, that identifies the wirelessdevice 14 within a wireless network.

The wireless device 14 may be any mobile communication device adapted tooperate within a wireless network, and is preferably a two-waycommunication device. The operation of the wireless device 14 may varydependent upon the wireless network in which the device 14 is intendedto operate. For example, a wireless device 14 that operates in NorthAmerican may include a communication subsystem designed to operate withthe Mobitex™ mobile communication system or the DataTAC™ mobilecommunication system, whereas a wireless device 14 that operates inEurope may incorporate a General Packet Radio Service (GPRS)communication system. Thus, the format of the wireless identification 26will depend upon the wireless protocol used by the particular wirelessnetwork in which the wireless device 14 operates. For example, wirelessdevices in the Mobitex network are identified using a Mobile AccessNumber (MAN).

In operation, the information source 12 receives a networkidentification 16, such as a domain name and host name identification,that is associated with the wireless device 14, and queries the networkserver 18 to determine a network address 24, such as an IP address,corresponding to the network identification 16. Using the networkaddress 24, the information source 12 then transmits data 11 through acomputer network to the virtual device manager 20. The informationsource may, for example, combine the network address 24 with the data 11in accordance with a network data transfer protocol in order to transferthe resultant data packet 28 over a computer network to the virtualdevice manager 20. The data packet 28 may also include a senderidentification for the information source (SDR ID), such as an IPaddress or domain name, to enable two-way communication with thewireless device 14. Upon receiving the data packet 28 from theinformation source 12, the virtual device manager 20 queries the addressresolution module 22 to determine a wireless identification 26, such asa MAN, for the wireless device 14 corresponding to the network address24. The wireless identification 26 is then combined with the data 11 andthe sender identification (SDR ID), for example in accordance with anappropriate wireless protocol, and the resultant data packet 30 istransmitted to the wireless device 14 over the wireless network.

FIG. 2 is a diagram illustrating one example implementation 40 of thesystem 10 shown in FIG. 1. This embodiment 40 includes an informationsource 42, a domain name server (DNS) 44, an address resolution (AR)module 46, a virtual device manager 48, and a mobile data system 50. Thesystem 40 also includes a DNS table 52 accessible by the DNS 44 and anAR table 54 accessible by the AR module 46. Also illustrated are awireless gateway 58, a wireless network 60, and a wireless device 62.

The DNS 44, AR module 46, virtual device manager 48, and mobile datasystem 50 are preferably included within the same local area network(LAN) and protected behind a common firewall. The information source 42is preferably also included within the LAN and protected behind thecommon firewall, but may alternatively communicate with the LAN througha wide area network (WAN).

The information source 42 uses a network identification to push dataover a virtual TCP/IP connection to the wireless device 62. In thisembodiment, the network identification associated with the wirelessdevice 62 preferably includes a host name that identifies the wirelessdevice 62 and a domain name that identifies the DNS 44. (See, e.g., FIG.3). Using the network identification, the information source 42 queriesthe DNS 44 through the LAN or WAN for a network address associated withthe wireless device 62. The network address may, for example, bedetermined by the DNS 44 by matching the network identification to acorresponding network address in the DNS table 52.

The network address is preferably one of a plurality of IP addressesassigned to the virtual device manager 48. The configuration of thevirtual device manager 48 within the local area network is based on anetworking technique called virtual host technology in which multiple IPaddresses are assigned to a single device, either statically ordynamically. The IP addresses assigned to the virtual device manager 48may be tied to one network interface or to multiple network interfaces,using a networking technique called virtual interface binding. Thisnetwork configuration provides a virtual TCP/IP stack for each IPaddress assigned to the virtual device manager 48, enabling the virtualdevice manager 48 to simulate multiple virtual devices, each having aTCP/IP stack.

Using the network address, the information source 42 transmits the datathrough the LAN or WAN to the virtual device manager 48. The virtualdevice manager 48 then queries the AR module 46, preferably using astandard address resolution protocol, to resolve the network addressinto a wireless identification, such as a MAN, that identifies thewireless device 62 within the wireless network 60. The AR module 46 may,for example, resolve the network address by matching it to acorresponding wireless identification in the AR table 54. (See, e.g.,FIG. 3) The AR table 54 may, for example, be a database that is storedin a memory device accessible by the AR module 46.

The mobile data system 50 receives the data and wireless identificationfrom the virtual device manager 48. The mobile data system 50 is asecure gateway between the virtual device manager 48 within thecorporate LAN and a wide area network (WAN) 56, such as the Internet,and transmits the data and wireless identification over the WAN 56 tothe wireless gateway 58. The mobile data system 50 preferably alsoconverts the data into a format compatible with the wireless device 62,encrypts and compresses the data into a data packet, and formats thedata packet and wireless identification for transmission over the WAN 58to the wireless gateway 58. The mobile data system 50 may also performadditional functions, as described in the following co-owned PCTapplications, which are hereby incorporated into the present applicationby reference: International Application No. PCT/CA02/01074, entitledSystem And Method For Pushing Data From An Information Source To AMobile Communication Device Including Transcoding Of the Data, filedJul. 12, 2002; International Application No. PCT/CA02/01072, entitledSystem And Method For Providing Remote Data Access For A MobileCommunication Device, filed Jul. 12, 2002; International Application No.PCT/CA02/01073, entitled System And Method For Providing Remote DataAccess And Transcoding For A Mobile Communication Device, filed Jul. 12,2002. In these related applications, however, the mobile data system 50is instead referred to as an “IP Proxy.” The terms “mobile data system”and “MDS” as used in the present application are therefore synonymouswith the term “IP Proxy” as used in the above-referenced incorporatedapplications.

The wireless gateway 58 provides an interface between the WAN 56 and thewireless network 60, which transmits the data packet to the wirelessdevice 62. The wireless gateway 58 may, for example, convert the databetween WAN protocols and wireless network protocols, address the datapacket for transmission over the wireless network using the wirelessidentification, store and forward data to and from the wireless device62, and perform other typical interface functions.

FIG. 3 is a diagram 70 showing one example of how data may be pushedfrom an information source 42 to a wireless device 62 using the systemof FIG. 2. In this example, the information source 42 first queries theDNS 44 to resolve the network identification “USER1.COMPANY.COM” into anIP address. In this case, the host name “USER1” corresponds to theparticular wireless device 62 to which the information is to bedelivered. Using the DNS table 52, the DNS 44 determines the IP address(192.100.01.01) corresponding to the network identification “USER1.COMPANY.COM,” and transmits the IP address over the network as aresponse to the information source 42. As illustrated, the DNS table 52may include a plurality (1−N) of network identifications and acorresponding plurality (1−N) of network addresses.

Having resolved the network identification, the information source 42uses the resultant IP address (192.100.01.01) to transmit the datathrough the LAN to the virtual device manager 48. As illustrated, thevirtual device manager 48 is assigned a plurality (1−N) of IP addressesin the network (i.e., 192.100.01.01-192.100.01.N), in order to emulate aTCP/IP stack for multiple wireless devices having access to the system.The virtual device manager 48 then queries the AR module 46 to resolvethe IP address (192.100.01.01) into an identification (2000AB1) of thewireless device 62 within the wireless network 60, as described above.The data and wireless identification (2000AB1) are then transmitted tothe mobile data system 50, which prepares the data for transport overthe WAN 56 to the wireless gateway 58, as described above.

FIG. 4 is a diagram of an example system for transmitting data 82 from afirst wireless device 84 through a computer network to a second wirelessdevice 86 using a network identification 88 associated with the secondwireless device 86. In addition to the first and second wireless devices84, 86, the system 80 includes a mobile data system 90, a network server92, a virtual device manager 94, and an address resolution (AR) module96.

The first and second wireless devices 84, 86 may be any two-way mobilecommunication devices adapted to operate within a wireless network. Thenetwork identification 88 and data 82 may be stored in a memory deviceon the first wireless device 84, or may be input to the wireless device84, for example through a user interface. The network identification 88may, for example, include a host name for the second wireless device 86and a domain name for the network server 92, but could alternatively besome other type of identification that uniquely identifies the secondwireless device 86 within a computer network.

The mobile data system 90 may, for example, be a processing deviceoperating in a computer network. The mobile data system 90 is operableto communicate with the first wireless device via the wireless networkand receive the data 82 and network identification 88 from the firstwireless device 84. In addition, the mobile data system 90 is coupledthrough a computer network to the network server 92 and the virtualdevice manager 94. In alternative embodiments, however, the mobile datasystem 90 may operate on the same processor as the network server 92and/or the virtual device manager 94.

The network server 92 may, for example, be a domain name server (DNS)operating in the computer network. The network server 92 is operable toreceive the network identification 88 from the mobile data system 90 andidentify a network address 98, such as an IP address, associated withthe network identification 88.

The virtual device manager 94 may, for example, be a processing deviceoperating in the computer network. The virtual device manager 94,similar to the virtual device manager 20 described above with referenceto FIG. 1, may be accessed on the computer network using any of aplurality of network addresses, with each network address correspondingto a different wireless device. The address resolution (AR) module 96,similar to the AR module 22 of FIG. 1, may be a software moduleexecuting on a processing device operating in the computer network, andin one embodiment may be executed by the virtual device manager 94. TheAR module 96 is operable to receive the network address 98 and identifya corresponding wireless identification 100 for the second wirelessdevice 86.

In operation, the first wireless device 84 receives data 82 and anetwork identification 88 that is associated with the second wirelessdevice 86, and combines the network identification 88 and data 82 into adata packet 102 for transmission over a wireless network and to themobile data system 90. The data packet 102 may also include a senderidentification (SDR ID) for the first wireless device, such as a networkidentification, IP address, or wireless identification, to enabletwo-way communication with the second wireless device. The mobile datasystem 90 then queries the network server 92 to resolve the networkidentification 88 into a network address 98, such as an IP address.Using the network address 98, the mobile data system 90 transmits thedata 82 through the computer network to the virtual device manager 20.The mobile data system 90 may, for example, combine the network address98 with the data 82 and sender identification (SDR ID) in accordancewith a network data transfer protocol in order to transfer the resultantdata packet 104 over the computer network to the virtual device manager94. Upon receiving the data packet 104 from the information source, thevirtual device manager 94 queries the AR module 96 to determine awireless identification 100, such as a MAN, for the second wirelessdevice. The wireless identification 100 is then combined with the data82 and sender identification (SDR ID) in accordance with the appropriatewireless network protocol, and the resultant data packet 106 istransmitted over the wireless network to the second wireless device 86.

FIG. 5 is a diagram illustrating one example implementation 110 of thesystem 80 of FIG. 4. This embodiment 110 includes a domain name server(DNS) 112, a mobile data system 114, a virtual device manager 116, andan address resolution (AR) module 118. The system also includes a DNStable 120 accessible by the DNS 44 and an AR table 122 accessible by theAR module 118. Also illustrated are a wireless gateway 124, a firstmobile device 126 operating within a first wireless network 128, and asecond wireless device 130 operating within a second wireless network132.

The DNS 112, mobile data system 114, virtual device manager 116, and ARmodule 118 are preferably included within the same local area network(LAN) 134, and are preferably separated from a wide area network (WAN)136, such as the Internet, by a common firewall. The first and secondwireless devices 126, 130 may operate within different wireless networks128, 132, as illustrated, but could alternatively operate within thesame wireless network.

In operation, data may be transmitted between the first and secondwireless devices 126, 130 using unique network identifications assignedto each of the wireless devices 126, 130. For example, in order totransmit data from the first wireless device 126 to the second wirelessdevice 130, a network identification for the second wireless device 130,such as a domain name and host name identification, may be input to thefirst wireless device 126 through a user interface. The first wirelessdevice 126 may then format the data and network identification using theappropriate wireless protocol, and transmit the resultant data packetover the wireless network 128 to the wireless gateway 124.

The wireless gateway 124 provides an interface between the wirelessnetwork(s) 128, 132 and the WAN 136, similar to the wireless gateway 58described above with reference to FIG. 2. The wireless gateway 124reformats the data for transmission over the WAN 136 and transmits thedata to the mobile data system 114.

The mobile data system 114 is a secure gateway between the LAN 134 andthe WAN 136, similar to the mobile data system 50 described above withreference to FIG. 2. Upon receiving data and a network identificationfrom the WAN 1136, the mobile data system 114 queries the DNS 114 toresolve the network identification into a network address, such as an IPaddress, associated with the second wireless device 130. The networkaddress may, for example, be determined by the DNS 112 by matching thenetwork identification to a corresponding network address in the DNStable 120. As described above with reference to FIG. 2, the networkaddress is preferably one of a plurality of IP addresses assigned to thevirtual device manager 48, which simulates a TCP/IP stack for multiplemobile devices 126, 130 within the system 110.

Having received the network address from the DNS 112, the mobile datasystem 114 uses the network address transfer the data to the virtualdevice manager 116 through the LAN 134. The virtual device manager 116queries the AR module 118, preferably using a standard addressresolution protocol, to resolve the network address into a wirelessidentification, such as a MAN, that identifies the second wirelessdevice 130 within the wireless network 132. The AR module 118 may, forexample, resolve the network address by matching it to a correspondingwireless identification in the AR table 122. (See, e.g., FIG. 6). The ARtable 122 may, for example, be a database in a memory device accessibleby the AR module 46. Having resolved the network address into a wirelessidentification, the virtual device manager 116 then sends the data andwireless identification back through the LAN to the mobile data system114 for transmission to the second wireless device 130.

The mobile data system 114 formats the wireless identification and thedata, and transmits the resultant data packet over the WAN 136 to thewireless gateway 124. In addition, the mobile data system 114 may alsoconvert the data into a format compatible with the wireless device 130,encrypt and compress the data, and perform additional functions, asdescribed above with reference to FIG. 2. The wireless gateway 124 thenconverts the data packet from the mobile data system 114 into a wirelessnetwork protocol, addresses the data packet for transmission over thewireless network 132 using the wireless identification, and transmitsthe data to the wireless device 130. As noted above, the wirelessgateway 124 may also perform other interface functions, for instance inthe case of multiple wireless networks 128, 132, the wireless gateway124 may determine which of the wireless networks 128, 132 was last incommunication with the wireless device 130.

FIG. 6 is a diagram 140 showing one example of how data may hetransmitted from a first wireless device 126 to a second wireless device130 using the system 110 of FIG. 5. In this example, the first wirelessdevice 126 transmits data to the mobile data system (MDS) 114 addressedwith the network identification “USER2.COMPANY.COM.” The host name“USER2” in this example identifies the second wireless device 130. TheMDS 114 then queries the DNS 112 to resolve the domain name and hostname into the IP address “192.100.01.02” using the DNS table 120. Asillustrated, the DNS table 120 includes a plurality (1−N) of networkidentifications and a corresponding plurality (1−N) of networkaddresses.

With the IP address (192.100.01.02) from the DNS table 120, the MDS 114opens a network connection with the virtual device manager 116, andsends the data to the virtual device manager 116 in order to resolve theIP address into a corresponding wireless identification (2000AB2) forthe second wireless device 130. As described above, the virtual devicemanager 116 is assigned a plurality (1−N) of IP addresses in the network(i.e., 192.100.01.01-192.100.01.N), in order to emulate a TCP/IP stackfor multiple wireless devices 126, 130. The virtual device manager 116queries the AR module 118 to resolve the IP address (192.100.01.02) intothe wireless identification (2000AB2) using the AR table 122. The datafrom the first wireless device 126 along with the wirelessidentification (2000AB2) are then transmitted back to the MDS 114, andfrom the MDS 114 to the second wireless device 130, as described above.

FIG. 7 is a diagram illustrating one example implementation 150 of thesystem 80 of FIG. 4 in which the first and second wireless devices 126,130 are associated with different local area networks 152, 154. Bothlocal area networks 152, 154 include a mobile data system (MDS 1 and MDS2) 156, 158, a virtual device module (VDM 1 and VDM 2) 160, 162, anaddress resolution (AR) module 164, 166, and a domain name server (DNS 1and DNS 2) 168, 170. Also illustrated are the first wireless device 126operating with a first wireless network 128 and a first wireless gateway172, and the second wireless device 130 operating with a second wirelessnetwork 132 and a second wireless gateway 174. It should be understood,however, that in other embodiments the first and second wireless devices126, 130 may operate within the same wireless network. It should also beunderstood that the system 150 could alternatively include a singlewireless gateway that interfaces multiple wireless networks 128, 132 tothe wide area network (WAN) 136.

Similar to the system 110 described above with reference to FIG. 5, datamay be transmitted in this system 150 between the first and secondwireless devices 126, 130 using unique network identifications assignedto each of the wireless devices 126, 130. For example, in order totransmit data from the first wireless device 126 to the second wirelessdevice 130, a network identification for the second wireless device maybe input to the first wireless device 126 through a user interface. Thefirst wireless device 126 formats the data and network identificationfor wireless transmission, and transmits the resultant data packet overthe wireless network 128 to the first wireless gateway 172. The wirelessgateway 172 reformats the data and network identification fortransmission over the WAN 136 and forwards it to the MDS 156 in thefirst LAN 152.

Upon receiving the data and network identification from the WAN 136, theMDS 156 in the first LAN 152 queries the DNS 168 to resolve the networkidentification. Because the second wireless device 130 in thisembodiment 150 operates in association with the second LAN 154, however,the network identification should identify the second LAN 154. Forexample, the network identification may include a host name identifyingthe second wireless device 130 and a domain name identifying the DNS 170in the second LAN 154. Therefore, upon being queried with the networkidentification, the DNS 168 in the first LAN 152 instructs its MDS 156to forward the data through the WAN 136 to the virtual device manager(VDM) 162 in the second LAN 154. The DNS 168 may, for example, accessthe DNS 170 in the second LAN 154 to provide the MDS 156 with a networkaddress within the WAN 136 for the VDM 162.

Similar to the virtual device managers described above, the VDM 162 inthe second LAN is preferably assigned a plurality of network addressesin order to simulate a TCP/IP stack for multiple mobile devicesoperating in association with the second LAN 154, including the secondmobile device 130. Having received the data and network address from thefirst LAN 152, the VDM 162 queries the AR module 166 in the second LAN154 to resolve the network address into a wireless identification, suchas a MAN, that identifies the second wireless device 130 within thewireless network 132. The data and wireless identification are thenforwarded to the MDS 158.

The MDS 158 in the second LAN 154 formats the wireless identificationand data and transmits it over the WAN 136 to the second wirelessgateway 124. The MDS 158 may also encrypt and compress the data, andperform additional functions as described above. The second wirelessgateway 174 converts the data packet received from the MDS 158 in thesecond LAN into a wireless network protocol, addresses the reformatteddata using the wireless identification, and transmits the resultant datapacket over the wireless network 132 to the second wireless device 130.

FIG. 8 is a diagram illustrating another example implementation 180 ofthe system 80 of FIG. 4 in which the first and second wireless devices126, 130 are associated with different local area networks 182, 184.Both local area networks 182, 184 include a mobile data system (MDS 1and MDS 2) 186, 188, a virtual device module (VDM 1 and VDM 2) 190, 192,and an address resolution (AR) module 194, 196. In addition, each of thelocal area networks 182, 184 are coupled to a common network server 198.

Similar to the system 150 described above with reference to FIG. 7, datamay be transmitted in this system 180 from the first wireless device 126to the second wireless device 130 via one or more wireless networks 128,132 and a wide area network (WAN) 136. For convenience, however, thewireless network(s) 128, 132, wireless gateway(s) 172, 174, and widearea network (WAN) 136 are not illustrated in FIG. 8.

In the system 180 of FIG. 8, a data packet destined for the secondwireless device 130 is transmitted from the first wireless device 126 tothe MDS 186 in the first LAN 182. In addition to its payload data, thedata packet transmitted from the first wireless device 126 may include asender identification of the first wireless device 126, such as awireless network identification, and either a network identification ora network address uniquely identifying the second wireless device 130.For example, the data packet may be addressed with an IP address in thesecond LAN 184 that is associated with the second wireless device 130,or may be addressed with a unique network identification, as describedabove.

Upon receiving the data packet from the first wireless device 126, theMDS 186 in the first LAN 182 queries the AR module 194 to resolve thesender identification of the first wireless device 126 into a uniquenetwork address, such as an IP address, associated with the firstwireless device 126. The AR module 194 may, for example, resolve thesender identification by matching it to a corresponding networkidentification in an address resolution (AR) table. Similar to thosedescribed above, the network address of the first wireless device 126 ispreferably one of a plurality of IP addresses assigned to the VDM 190 inthe first LAN 182, which simulates a TCP/IP stack for multiple mobiledevices.

In addition, the MDS 186 in the first LAN 182 also opens a communicationlink with the network server 198, for example through a WAN. The networkserver 198 maintains a table, such as an electronic database, thatassociates unique network identifications for the wireless devices 126,130 with network addresses in the first or second LAN 182, 184. The MDS186 queries the network server 198 to resolve the network address forthe first wireless device 126 into a network identification for thefirst wireless device. In addition, if the network address for thesecond wireless device 130 was not provided in the data packettransmitted from the first wireless device 126, then the MDS 186 alsoqueries the network server 198 to resolve the network identification ofthe second wireless device 130 into a network address, such as an IPaddress, in the second LAN 184.

With the network address for the second wireless device 130, the MDS 186opens a connection, for example through a WAN, to transmit the data andnetwork identification of the first wireless device 126 to the VDM 192in the second LAN 184. Similar to those described above, the networkaddress of the second wireless device 130 is preferably one of aplurality of IP addressed assigned to the VDM 192 in the second LAN 184.Having received the data and network identification from the first LAN182, the VDM 192 in the second LAN 184 queries the AR module 196 toresolve the network address for the second wireless device 130 into awireless identification, such as a MAC address, that identifies thesecond wireless device 130 within a wireless network.

From the VDM 192, the data is forwarded to the MDS 188 along with thewireless identification of the second wireless device 130 and thenetwork identification of the first wireless device 126. The MDS 188opens a connection with the network server 198, for example over a WAN,and queries the network server 198 to resolve the network identificationof the first wireless device 126 into the associated network address.The MDS 188 then formats the data for transmission to the secondwireless device 130 along with the wireless identification of the secondwireless device 130 and the network address and network identificationfor the first wireless device 126.

This written description uses examples to disclose the invention,including the best mode, and also to enable a person skilled in the artto make and use the invention. The patentable scope of the invention isdefined by the claims, and may include other examples that occur tothose skilled in the art.

1. A method comprising: using a network address to transmit informationto a device manager for delivery to a communication device, the devicemanager being accessible using a plurality of network addresses, eachnetwork address associated with the device manager and with a differentcommunication device; receiving, at the device manager, the informationover the network from a communication device using a network address ofthe device manager that is associated with the communication device;determining, by the device manager and from the network address,identifying information that identifies the communication device withina communication network; and transmitting the information, along withthe identifying information, over the communication network for deliveryto the communication device.
 2. The method of claim 1 wherein thecommunication device is a wireless communication device and thecommunication network is a wireless network.
 3. The method of claim 1wherein the network address includes a domain name and a host name. 4.The method of claim 1 wherein the network address is an internetprotocol (IP) address.
 5. A system comprising: a device manager that isaccessible over a network using a plurality of network addresses, eachnetwork address associated with the device manager and with a differentcommunication device; the device manager being configured to receiveinformation over the network from a communication device using a networkaddress of the device manager that is associated with the communicationdevice; the device manager being further configured to use the networkaddress associated with the communication device to determineidentifying information that identifies the communication device withina communication network; and the device manager being further configuredto transmit the information along with the identifying information tothe communication network for delivery to the communication device. 6.The system of claim 5 wherein the communication device is a wirelesscommunication device, and the communication network is a wirelessnetwork.